found a bug. It looks like it will grab text from before the word to correct:

Autocorrected layeqpayed to layeqpaid
Autocorrected payed to paid
Autocorrected laypaiedpayed to laypaiedpaid

Mostly was trying to trigger "payed", but if you don't have a space before the word, it will include everything up til the last space/terminator character.

Not a bug, but a limitation on how the algorithm works

It has no concept of "words" , we just have a stream of chars in which we find for patterns to be replaced (since we can use spaces to hopefully correctly delimit words, my code does so)

I dont think there's a way of fixing this issue without major changes to the correction code

PS: Anyway it doesnt feel like a very common scenario to run into

Yeah. And this issue isn't a stopping issue. However, I think that because this change makes this more obvious, a note about this behavior should be added as it will likely come up more often if/when people can render the "word".